Resin's `pomegranate' - auto-magical-loading maven jar dependencies for a project - but how to generate jars with pom.xml for them?

My understanding of the Pomegranate Draft specification is that.

My understanding of the Pomegranate Draft specification is that: Servlet containers can use pomegranate as an extension to the WEB-INF/lib with the following benefits: Shared . Jar files in a common repository, simplifying management and reducing . War sizes Library dependency resolution, including the ability to handle sub-module incompatibilities Familiar Maven pom.

Xml files, to take advantage of current development practices. Optional integration with Servlet web-app containers Optional integration with Java CanDI (JSR-299) managers ... The web-app may contain an optional WEB-INF/pom. Xml declaring the web-app's own dependencies.So I guess the idea is to mark the dependencies as "provided" in the war pom.

Xml and to add them in WEB-INF/pom. Xml for a deployment on Resin. I've not tested this though, so I might be wrong.

Actually, this pomegranate looks interesting but I don't get it entirely for now. While I understand its benefits, it seems to make the WAR not portable which is a big drawback. I'll dig it a bit further... (EDIT: I'm putting an answer to a comment from the OP below) To be honest, I don't find the spec draft very clear.

However, I found this pomegranate modules post on Caucho's blog that details a bit more how to get it working for a webapp: Pomegranate is designed to solve the module versioning and classloader issues from an enterprise-application perspective. Although we’re doing a bit of classloader magic behind the scenes, the developer perspective is fairly simple and clean: remove jars from your . War drop them in Resin’s project-jars directory declare jar dependencies in Maven pom files import them to your web-app with WEB-INF/pom.

Xml or in your resin-web. Xml At least, I understand these steps and they answer your question: you have to drop the jars manually in Resin's project-jars directory. That's not what I was expecting but I think that I was misunderstanding what pomegranate is all about.

If I'm not wrong, pomegranate is a kind of alternative to OSGI, it is about module bundling and classloading voodoo. It uses Maven's conventions to describe dependencies but it's not about dependencies management.

Or do You have to provide them in /project-jars/ dir, which the documentation calls a 'repository' but does not say what is it structure. Just throwing in the jars won't work. – Horacy Oliwka Nov 3 '09 at 7:01 I added details to my initial answer to cover this.

– Pascal Thivent Nov 3 '09 at 10:28.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.